Release 10.1A: OpenEdge Data Management:
Database Administration

Using the Schema Mover after conversion

After converting a Progress Version 9 database to an OpenEdge Release 10 database, it is possible to separate the schema and user data by using PROUTIL dump and load or bulkload qualifiers, the Database Administration Tool, the Data Dictionary, or 4GL code. However, as long as schema remains in an area, the extents continue to hold disk space, even after the removal of data. To free this disk space, use the Schema Mover qualifier to PROUTIL to move the schema. Once the area’s schema is moved the area can be truncated.

To move schema to a new area:

Truncate the database’s BI file. PROUTIL will send an error message if you do not.
Back up the database.
Caution: PROUTIL with the MVSCH qualifier is a non-recoverable utility. If the execution fails, you cannot connect to the database, and must restore a backup.
Enter the following syntax to begin the schema move, where dbname is the name of the converted database:

proutil dbname -C mvsch

As shown in Figure 1–1, after you convert your database to OpenEdge Release 10, Area 6 (NewDB.db) contains both the database’s schema and data. When you initiate the schema move by entering the syntax shown in Step 3, PROUTIL finds the next unused data area (starting at Area 7) and creates the target data area and the target data area’s extent. After creating the target data area, PROUTIL moves the schema from NewDB.db to NewDB_7.d1. All the schema records and indexes are deleted from NewDB.db. PROUTIL opens the .d1 files of the NewDB.db and NewDB_7.d1 and then updates and switches the master and area blocks. After the switch, the areas and their extents are renamed. Now that the schema is gone from the “Old Default Area,” you can truncate it and recover any unused space.

Figure 1–1: How the Schema Mover works

Note: Data in the “Old Default Area” not moved prior to area truncation will be lost.